Indication of Support for Keep-Alive

TCP Wake-Up: Reducing Keep-Alive Traffic in Mobile IPv4 and IPsec NAT Traversal

Applications such as instant messaging and push email require long-lived connections between clients and servers. In the absence of other traffic, stateful firewalls and Network Address Translators (NATs) require “keep-alive” messages to maintain state for such persistent connections. We present new measurements analyzing the energy consumption of these keep-alive messages on a mobile phone in ...

NAT Traversal Capability and Keep-Alive Functionality with IPSec in IKEv2 Implementation

Since IPv4 Private Networks are behind NAT (Network Address Translation) devices. So, to bypass the Binding Update and Binding Acknowledgment by NAT, we need to encapsulate it in UDP (User datagram Protocol) Packets. Hence, the Dual Stack Mobile IPv6 should support NAT Traversal and Detection. So for proper securing and fully functionality of NAT traversal, it should be IP Security Protected. P...

Why Keep Them Alive

Exploring Tradeoffs in Failure Detection in Routing Overlays

One of the key reasons overlay networks are seen as an excellent platform for large scale distributed systems is their resilience in the presence of node failures. This resilience rely on accurate and timely detection of node failures. Despite the prevalent use of keep-alive algorithms in overlay networks to detect node failures, their tradeoffs and the circumstances in which they might best be...

Using current uptime to improve failure detection in peer-to-peer networks

Peer-to-Peer (P2P) networks share computer resources or services through the exchange of information between participating nodes. These nodes form a virtual network overlay by creating a number of connections with one another. Due to the transient nature of nodes within these systems any connection formed should be monitored and maintained to ensure the routing table is kept up-to-date. Typical...